gpio: Add GPIO Definitions for H562/3 & H573 families #32
Conversation
| PA12: (pa12, 12, [1, 3, 5, 6, 7, 8, 9, 10, 15]), | ||
| PA13: (pa13, 13, [0, 15], crate::gpio::Debugger), | ||
| PA14: (pa14, 14, [0, 15], crate::gpio::Debugger), | ||
| PA15: (pa15, 15, [0, 1, 2, 4, 5, 6, 7, 8, 11, 12, 13, 14, 15], crate::gpio::Debugger), |
There was a problem hiding this comment.
If this is considered a debug pin(JTDI) then it should be for H503 too?
There was a problem hiding this comment.
PA15 is marked as such for the H503
|
@usbalbin I got a bit trigger happy with that debugger initial state, it seems! Fixed it so only pins listed in the reference manual as being in an alternate function push-pull configuration for debugging were marked as such. |
I am not familiar with what it affect or does in the hal, just noticed the difference between the MCUs |
It marks these pins as being in an alternate function initial state on reset, instead of the analog state all other GPIOs reset to: |
|
@usbalbin Anything blocking getting your approval on this? I'll merge if you +1 this so we can move on to including the H523/H533 GPIOs. |
This adds the required definitions to use the GPIO driver on H562/3 & H573 parts.